default to CertificateValidity::INVALID
authorCaolán McNamara <caolanm@redhat.com>
Mon, 8 Feb 2021 17:05:28 +0000 (17:05 +0000)
committerRene Engelhard <rene@debian.org>
Sat, 25 Mar 2023 13:04:55 +0000 (13:04 +0000)
commitc9a0462de804a3716795c73cc8a3d733b5fcf7ed
tree6b5e801b9bc2ce6d1e55f375be9d3754f97ee379
parentfa0c4f0a456f036b4487289afbe29a0039b3ec6d
default to CertificateValidity::INVALID

so if CertGetCertificateChain fails we don't want validity to be
css::security::CertificateValidity::VALID which is what the old default
of 0 equates to

notably

commit 1e0bc66d16aee28ce8bd9582ea32178c63841902
Date:   Thu Nov 5 16:55:26 2009 +0100

    jl137:  #103420# better logging

turned the nss equivalent of SecurityEnvironment_NssImpl::verifyCertificate
from 0 to CertificateValidity::INVALID like this change does

Change-Id: I5350dbc22d1b9b378da2976d3b0abd728f1f4c27
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/110561
Tested-by: Jenkins
Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
Gbp-Pq: Name default-to-CertificateValidity::INVALID.diff
xmlsecurity/source/xmlsec/mscrypt/securityenvironment_mscryptimpl.cxx